Early Launch Antimalware, Boot-Start Driver Initialization Policy must prevent boot drivers identified as bad.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-63607	WN10-CC-000085	SV-78097r1_rule		Medium

Description
Compromised boot drivers can introduce malware prior to protection mechanisms that load after initialization. The Early Launch Antimalware driver can limit allowed drivers based on classifications determined by the malware protection application. At a minimum, drivers determined to be bad must not be allowed.

STIG	Date
Windows 10 Security Technical Implementation Guide	2016-10-28

Details

Check Text ( None )
None

Fix Text (F-69537r1_fix)
The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy is to enforce "Good, unknown and bad but critical" (preventing "bad"). If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected.

Fix Text (F-69537r1_fix)

The default behavior is for Early Launch Antimalware - Boot-Start Driver Initialization policy is to enforce "Good, unknown and bad but critical" (preventing "bad").

If this needs to be corrected or a more secure setting is desired, configure the policy value for Computer Configuration >> Administrative Templates >> System >> Early Launch Antimalware >> "Boot-Start Driver Initialization Policy" to "Not Configured" or "Enabled" with any option other than "All" selected.